Folk teleology drives persistence judgments

Two separate research programs have revealed two different factors that feature in our judgments of whether some entity persists. One program—inspired by Knobe—has found that normative considerations affect persistence judgments. For instance, people are more inclined to view a thing as persisting when the changes it undergoes lead to improvements. The other program—inspired by Kelemen—has found that teleological considerations affect persistence judgments. For instance, people are more inclined to view a thing as persisting when it preserves its purpose. Our goal in this paper is to determine what causes persistence judgments. Across four studies, we pit normative considerations against teleological considerations. And using causal modeling procedures, we find a consistent, robust pattern with teleological and not normative considerations directly causing persistence judgments. Our findings put teleology in the driver’s seat, while at the same time shedding further light on our folk notion of an object

Truthmaker Commitments

On the truthmaker view of ontological commitment [Heil (From an ontological point of view, 2003); Armstrong (Truth and truthmakers, 2004); Cameron (Philosophical Studies, 2008)], a theory is committed to the entities needed in the world for the theory t

Detecting, Isolating and Enforcing Dependencies Between and Within Test Cases

Testing stateful applications is challenging, as it can be difficult to identify hidden dependencies on program state. These dependencies may manifest between several test cases, or simply within a single test case. When it's left to developers to document, understand, and respond to these dependencies, a mistake can result in unexpected and invalid test results. Although current testing infrastructure does not currently leverage state dependency information, we argue that it could, and that by doing so testing can be improved. Our results thus far show that by recovering dependencies between test cases and modifying the popular testing framework, JUnit, to utilize this information, we can optimize the testing process, reducing time needed to run tests by 62% on average. Our ongoing work is to apply similar analyses to improve existing state of the art test suite prioritization techniques and state of the art test case generation techniques. This work is advised by Professor Gail Kaiser

Unit Test Virtualization with VMVM

Testing large software packages can become very time intensive. To address this problem, researchers have investigated techniques such as Test Suite Minimization. Test Suite Minimization reduces the number of tests in a suite by removing tests that appear redundant, at the risk of reducing fault-finding ability since it can be difficult to identify which tests are truly redundant. We take a completely different approach to solving the same problem of long running test suites by instead reducing the time needed to execute each test, an approach that we call Unit Test Virtualization. We describe the empirical analysis that we performed to ground our approach and provide an implementation of Unit Test Virtualization targeting Java applications. We evaluated our implementation, VMVM, using 20 real-world Java applications and found that it reduces test suite execution time by up to 97 percent (on average, 62 percent) when compared to traditional unit test execution. We also compared VMVM to a well known Test Suite Minimization technique, finding the reduction provided by VMVM to be four times greater, while still executing every test with no loss of fault-finding ability

Dynamic Taint Tracking for Java with Phosphor (Demo)

Dynamic taint tracking is an information flow analysis that can be applied to many areas of testing. Phosphor is the first portable, accurate and performant dynamic taint tracking system for Java. While previous systems for performing general-purpose taint tracking in the JVM required specialized research JVMs, Phosphor works with standard off-the-shelf JVMs (such as Oracle's HotSpot and OpenJDK's IcedTea). Phosphor also differs from previous portable JVM taint tracking systems that were not general purpose (e.g. tracked only tags on Strings and no other type), in that it tracks tags on all variables. We have also made several enhancements to Phosphor, allowing it to track taint tags through control flow (in addition to data flow), as well as allowing it to track an arbitrary number of relationships between taint tags (rather than be limited to only 32 tags). In this demonstration, we show how developers writing testing tools can benefit from Phosphor, and explain briefly how to interact with it

Evaluating the Business Value of CPOE for Cancer Care in Australia: A Resource Based View Perspective

Today, cancer is one of the leading causes of death throughout the world. This threatening disease has huge negative impacts, not only on quality of life, but also on the healthcare industry, whose resources are already scarce. Thus, finding new approaches for cancer care has been a central point of interest during the last few decades. One of these approaches is the use of computerised physician order entry (CPOE) systems, which have the potential to provide more effective and efficient patient centric cancer care. This paper serves to examine the business value of an American CPOE in an Australian context. This is achieved by using our specifically designed tool to evaluate the business value of IT in the healthcare in combination with a resource based view perspective. Our results show that the system has a number of enabling resources to generate business value subject to having other resources